Sequential power up of devices in a computing cluster based on relative commonality

ABSTRACT

A computer program product includes computer usable program code for: identifying a plurality of power distribution units (PDUs) disposed in a rack, wherein each PDU receives power from a main power source and includes a circuit breaker; identifying a plurality of devices disposed in the rack, wherein each device receives power from one of the PDUs, and wherein the plurality of devices are selected from server nodes, network switches and external data storage devices; obtaining vital product data from a service processor in each device, wherein the vital product data identifies the device by a model identification code; and powering on, for each of the PDUs, the plurality of devices that are connected to the PDU in a sequence to prevent an inrush current from tripping the circuit breaker within the PDU, wherein the sequence powers on devices in order of ascending commonality of the model identification code.

BACKGROUND

1. Field of the Invention

The present invention relates to methods of providing electrical powerto the devices in a computing cluster, and more particularly relates tomethods of sequencing the power up of devices in a cluster or datacenter.

2. Background of the Related Art

High performance computing clusters contain a large number of servernodes, network switches, and data storage devices. There are times whenthe entire cluster of such information technology equipment needs to bepowered-off for service. When these cluster entities are powered backon, there is a large inrush of electrical current from the main powerdistribution center. This inrush current can trip a circuit breaker atthe main distribution center or it can trip a circuit breaker at theindividual power distribution units (PDUs) that are positioned withinthe individual racks of the cluster. A common way to limit the inrush ofelectrical current is to add inductors to the input of each power supplyso that the resistor-inductor-capacitor (R-L-C) circuit slowly ramps upthe current supplied to the design.

BRIEF SUMMARY

One embodiment of the present invention provides a method of powering ona plurality of devices. The method includes identifying a plurality ofpower distribution units disposed in a rack, wherein each powerdistribution units is connected to received power from a main powersource, and wherein each power distribution unit includes a circuitbreaker. The method further includes identifying a plurality of devicesdisposed in the rack, wherein each device is connected to receive powerfrom one of the power distribution units, and wherein the plurality ofdevices are selected from server nodes, network switches and externaldata storage devices. Vital product data is obtained from a serviceprocessor in each device, wherein the vital product data identifies thedevice by a model identification code. For each of the powerdistribution units, the plurality of devices that are connected to thepower distribution unit are powered on in a sequence to prevent aninrush current from tripping the circuit breaker within the powerdistribution unit, wherein the sequence powers on devices in order ofascending commonality of the model identification code.

Another embodiment of the invention provides a computer program productincluding computer usable program code embodied on a tangible computerusable storage medium. The computer program product includes computerusable program code for identifying a plurality of power distributionunits disposed in a rack, wherein each power distribution units isconnected to received power from a main power source, and wherein eachpower distribution unit includes a circuit breaker; computer usableprogram code for identifying a plurality of devices disposed in therack, wherein each device is connected to receive power from one of thepower distribution units, and wherein the plurality of devices areselected from server nodes, network switches and external data storagedevices; computer usable program code for obtaining vital product datafrom a service processor in each device, wherein the vital product dataidentifies the device by a model identification code; and computerusable program code for powering on, for each of the power distributionunits, the plurality of devices that are connected to the powerdistribution unit in a sequence to prevent an inrush current fromtripping the circuit breaker within the power distribution unit, whereinthe sequence powers on devices in order of ascending commonality of themodel identification code.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

FIG. 1 is a graph showing the relationship of inrush current at initialpower on of an example circuit compared to the operational current ofthe same circuit.

FIG. 2 is a diagram of a rack having several servers coupled to each ofthe several power distribution units (PDUs).

FIG. 3 is a diagram of a server aligned for contact with an addressplate in a given position within a rack.

FIG. 4 is a diagram of a server aligned in contact with rackidentification wires and the address plate.

FIG. 5 is a block diagram of a system having a plurality of serverscoupled to a plurality of power distribution units.

FIG. 6 is a diagram of a computer capable of serving as a centralmanagement entity.

FIG. 7 is a flowchart of a method of the present invention in which amanagement entity controls a power up sequence.

DETAILED DESCRIPTION

One embodiment of the present invention provides a method of powering ona plurality of devices. The method includes identifying a plurality ofpower distribution units disposed in a rack, wherein each powerdistribution units is connected to received power from a main powersource, and wherein each power distribution unit includes a circuitbreaker. The method further includes identifying a plurality of devicesdisposed in the rack, wherein each device is connected to receive powerfrom one of the power distribution units, and wherein the plurality ofdevices are selected from server nodes, network switches and externaldata storage devices. Vital product data is obtained from a serviceprocessor in each device, wherein the vital product data identifies thedevice by a model identification code. For each of the powerdistribution units, the plurality of devices that are connected to thepower distribution unit are powered on in a sequence to prevent aninrush current from tripping the circuit breaker within the powerdistribution unit, wherein the sequence powers on devices in order ofascending commonality of the model identification code.

In a preferred embodiment, the step of determining the order ofascending commonality is performed by tabulating the number of deviceshaving a given model identification code and sorting a list of modelidentification codes from those having the fewest tabulated number ofdevices to those having the greatest tabulated number of devices. Themodel identification codes are typically stored in the vital productdata of a device, such as a server, network switch or data storagedevice. This vital product data may be communicated from the BMC orother service processor of the individuals devices to a centralmanagement entity. The central management entity may store the modelidentification codes and tabulate them. The number of instances of anyparticular model identification code represents a device's commonality.The devices having the least commonality (i.e., fewest number of deviceswith the same model identification code) are viewed as performing aspecialized role or function in the cluster and are, therefore, given ahigher priority in the power on sequence. For example, if a clusterincludes a quantity of four x3650 M4 servers and a quantity of twohundred (200) HS23 servers (x3650 M4 servers and HS23 servers are bothavailable from International Business Machines Incorporation of Armonk,N.Y.), then it can be assumed that the role of the x3650 M4 servers havegreater importance in the cluster, and should be given a higherprioritization in the power on sequence, than the x3650 M4 servers.

The sequence may include powering on more than one of the devices at atime, so long as the inrush current to those devices will not trip thecircuit breaker of the power distribution unit providing power to thosedevices. The sequence may also wait a predetermined period of timebetween powering on any one or more device and subsequently powering onany further device connected to the same power distribution unit.Waiting for a period of time allows the inrush current to settle down.In yet another embodiment, the sequence of powering on the plurality ofdevices in a cluster may be implemented to also prevent the cumulativeinrush current to the cluster from tripping a circuit breaker within themain power source that is connected to provide power to each of thepower distribution units.

In a further embodiment, the method further includes identifying therack position of each device with the rack, wherein the rack positiondetermines the power distribution unit to which the device is connected.Optionally, the rack position of each device is identified by eachdevice detecting a rack position and communicating the detected rackposition to a central management entity.

A still further embodiment of the method may include quantitativemethods to assure that the devices powered on in any one step of thesequence will not trip the circuit breaker of the power distributionunit from which those devices receive power. One such method determinesa peak inrush current for each of the plurality of devices, anddetermines a current rating for the circuit breaker in each of theplurality of power distribution units. Then, the method determines asequence that, for each of the plurality of distribution units, willpower on the plurality of devices without causing a cumulative peakinrush current through the power distribution unit that exceeds thecurrent rating for the circuit breaker in the power distribution unit.The cumulative peak inrush current is the sum of the peak inrush currentthrough the power distribution unit to all of the devices beingsimultaneously powered on at any point in the sequence. The peak inrushcurrent for each device may be measured, but may also be estimated as apredetermined multiple of the nominal current rating of the device. Forexample, the peak inrush current for a server is typically between 12and 20 times the server's nominal current rating. The nominal currentrating of the device may be included in a device's vital product data,which may be obtained from a service processor in the device.

Another embodiment of the invention provides a computer program productincluding computer usable program code embodied on a tangible computerusable storage medium. The computer program product includes computerusable program code for identifying a plurality of power distributionunits disposed in a rack, wherein each power distribution units isconnected to received power from a main power source, and wherein eachpower distribution unit includes a circuit breaker; computer usableprogram code for identifying a plurality of devices disposed in therack, wherein each device is connected to receive power from one of thepower distribution units, and wherein the plurality of devices areselected from server nodes, network switches and external data storagedevices; computer usable program code for obtaining vital product datafrom a service processor in each device, wherein the vital product dataidentifies the device by a model identification code; and computerusable program code for powering on, for each of the power distributionunits, the plurality of devices that are connected to the powerdistribution unit in a sequence to prevent an inrush current fromtripping the circuit breaker within the power distribution unit, whereinthe sequence powers on devices in order of ascending commonality of themodel identification code. It should be recognized that the computerprogram product may include further computer usable program code toimplement one or more additional steps or aspects of the methodsdescribed herein.

FIG. 1 is a graph showing the relationship of inrush current at initialpower on of an example circuit compared to the operational current ofthe same circuit. EN is the enable signal to a power supply that allowsthe voltage to be turned on. I_(IN) is the current provided to the powersupply to allow the output voltage to be supplied. V_(OUT) is the outputvoltage from the power supply to the circuit, such as a server.

The EN signal had a scale of 500 mV/division on the vertical axis, suchthat the EN voltage goes from 0 volts to 1.0 volts. The current I_(IN)is shown with a scale of 50 mA/div, such that the inrush currenttemporarily rises from 0 mA to about 110 mA, whereas the nominaloperating current is about 5 mA. Accordingly, the inrush current can benearly 20 times the nominal operating current rating. The V_(OUT) scaleis 200 mV/division, such that the voltage goes form 0 volts to about 1.3volts. The x-axis represents the passage of time, where each division onthe horizontal axis represents 20 microseconds (μs). So if the EN enablesignal starts at t=0 microseconds, the output voltage starts to riseafter about 130 microseconds and reaches its full value of 1.3 V atabout 147 microseconds. Turning on a given circuit will produce aquantifiable inrush current, but this figure is only intended as aqualitative representation of what would happen in a server. Actualmeasurements of the maximum nominal current and peak inrush current forseveral representative devices are provided in Table 1, below, where theduration of the inrush current is measured in milliseconds (ms).

TABLE 1 Relationship of nominal current and inrush current inrepresentative devices Maximum Nominal Peak Inrush Equipment CurrentCurrent HP Proliant DL 360 G4 - 2.4 A  61 A for 3 ms IU server HPProliant e-class 1.6 A 100 A for 2 ms blade server IBM BladeCenter,fully 23.7 A  200 A for 4 ms loaded IBM x-series 260 4.9 A 120 A for 4ms Cisco 3825 Router   2 A  50 A for 10 ms

A typical PDU circuit breaker will trip at a current that is somewherebetween 12 to 20 times the rated current of the PDU. For example, a 30Amp PDU can sustain 360 AMPs to 600 AMPs for a short period. For a groupof IBM xSeries 260 servers, with an inrush current of 120 amps each (asshown in Table 1, above), it is theoretically possible to simultaneouslyturn on up to five of the servers coupled to a single 30 Amp PDU, sincethe total current inrush of 600 Amps (5×120 Amps) would not exceed the600 Amps that the circuit breaker than momentarily accept. However, amuch more conservative operation would turn on fewer than five serversat a time. A preferred method would execute a sequence that turns onjust two such servers at a time, then waits, and then turns on two moreservers. For a PDU powering a group of eight (8) servers, acorresponding power on sequence might include four steps. By using avery conservative number of devices to be simultaneously turned onthrough a single PDU, it is not necessary to perform actual calculationsto verify that the total inrush current will not trip the PDU circuitbreaker.

FIG. 2 is a diagram of two side-by-side racks (Rack 1 and Rack 2) 10,where each rack supports the operation of several servers 20. Theservers are shown as “1U” servers, but the servers need not all have thesame form factor. However, each server 20 is coupled to one of theseveral power distribution units (PDUs) 30. Each rack illustrates adirect, laterally adjacent relationship between a PDU and a group(subset) of the servers that are connected to receive power from thePDU. As shown, PDU #1 supplies power to the eight servers receivedwithin rack bays 35-42, which are directly laterally adjacent the PDU#1.

Methods of the invention reduce the inrush current so that a circuitbreaker is less likely to be tripped than when every server is poweredon simultaneously. The power on command is distributed across a numberof PDUs in a cluster at a controlled rate so that no one PDU has aninrush current that would trip its circuit breaker. However, theindividual devices are powered on in a logical sequence or order acrossthe cluster until all the servers and other devices are powered on.

The sequential powering on of the devices relies upon a certain periodof time passing between each step in the sequence, so that the inrushcurrent, which results from powering on a first set of devices, canquiet down before proceeding to power on a second set of devices in thesequence. The amount of time needed for the inrush current to quiet downor reach a value near the nominal operating current is dependent uponthe circuit for a device. Although it is possible to measure the exacttime period that each device requires for the inrush current to settle,a conservative time delay of about 100 to 500 microseconds may beadopted for all devices in a server environment.

Since the cluster has a plurality of PDUs distributing power in parallelto each other, servers and other devices within the cluster may also beturned on in parallel. However, the servers connected to any oneparticular PDU should be turned on in a sequential manner. Still, if thePDU has a sufficient current rating, then more than one server may beturned on during any one step in the sequence.

FIG. 3 is a diagram of a device 20, such as a server or PDU, aligned forcontact with an address plate 12 in a given position within a rack. Eachdevice 20 can determine its own position within the rack and communicatethat position to a central management entity, such as an xCAT managemententity (available from International Business Machines Corporation ofArmonk, N.Y.). Rack positions may be selected from a known number andarrangement of bays within the rack, such as following a standardconfiguration of “1U” bays. For example, a server 20 can detect its ownposition using a plurality of spring-loaded electrical pickups 22 formedalong a back surface 24 of the server and aligned for contact with anequal plurality of contacts 14 on an address plate securing within therack. As shown, there are six pickups 22 aligned with six contacts 14.The contacts 14 on each address plate 12 are either conductive ornon-conductive and are arranged to provide a unique binary coderepresenting a known location in the rack. Optionally, a non-conductivecontact may represent a “0” and a conductive contact may represent a“1”. When the contacts 14 are arranged for contact with thespring-loaded electrical pickups 22, the server 20 is able to read theaddress that represents its location within the rack. For example, theaddress shown is binary “1 1 0 1 0 0”, which equates to position 11within the rack. A PDU may similarly detect its own position. Based upona consistent practice of connecting a server 20 to a power distributionunit 30 based upon their relative positions within the rack (See FIG.2), such as making power connections directly laterally, the relativepositions can be considered to be determinative of which servers areconnected to which PDUs.

FIG. 4 is a diagram of a device 20, such as a server or a PDU, alignedin contact with rack identification wires 16 and the address plate 12.Accordingly, each device may detect a rack identification or address forthe rack in which the device is positioned. For example, a rackidentification card 18 may be added to the rack and may include abattery and electrical wires 16 that run down a vertical frame of therack. The rack identification card 18 includes a unique rack addressthat is placed onto the wires 16 that run from the card connection downthe rack frame. As described above for position detecting within a rack,the installed server or PDU may include electrical pickups 22 that arealigned for contact with the wires 16 along the vertical frame. Forexample, a plurality of wires may be selectively coupled to a battery orground in order to comprise a binary rack identification number. Oneillustration of the location of a device 20 may be represented asRack#-U#, which is a concatenation of the rack identification (Rack #)and the U position (U#) of the device, such as the servers 20 in racks10 shown in FIG. 2.

FIG. 5 is a block diagram of a system having a plurality of servers 20coupled to a plurality of power distribution units 30. Morespecifically, the system has a first group of servers (Servers 1-7) thateach have a power supply 26 connected to receive power from a first PDU(PDU 3) via power cables 40 and a second group of servers (Servers36-42) that each have a power supply 26 connected to receive power froma second PDU (PDU 1) via power cables 40. As shown, the Servers 1-7 aredirectly laterally adjacent PDU 1 and Servers 36-42 are directlylaterally adjacent PDU 3. While the power cables may be manuallyconnected, the servers 20 and the PDUs 30 include position detectors(PD) 22 consistent the spring-loaded electrical pickups of FIGS. 3-4.Each server 20 has a baseboard management controller (BMC) 24 that cancommunicate the server's detected position to the central managemententity 100 and each PDU has a service processor 34 that can communicatethe PDU's detected position to the central management entity 100. Basedupon the direct laterally adjacent positions detected, the centralmanagement entity 100 can determine that which servers are connected towhich PDU. These PDU-server associations are stored in the PDU-ServerAssociation Table 101.

Each server 20 also includes vital product data 28 about the server, andeach PDU 30 also includes vital product data 38 about the PDU. The vitalproduct data 28 of the server 20 may include the server's nominalcurrent rating and the server's role in the cluster. Accordingly, theBMC 28 may share the vital product data 28 with the central managemententity 100, where the central management entity 100 may store thenominal current rating in a table 102 and store the server's role orfunction in a table 103. Similarly, the vital product data 38 of the PDU30 may include the PDU's nominal current rating, such that the serviceprocessor 34 may share the vital product data 38 with the centralmanagement entity 100, such as for storage in the current ratings table102.

According to various embodiments of the invention, the centralmanagement entity 100 may consider the data in the PDU-ServerAssociation Table 101, the PDU & Server Current Ratings Table 102, andthe Server Model Identification Table 103 in determining a power onsequence for the devices in the cluster. It should be recognized thatany one or more of the servers 20 in the cluster of FIG. 5 may besubstituted with a network switch, and Table 103 could also includemodel identification codes for network switches, storage devices, andyet other devices, without other modification of the descriptionprovided herein. Accordingly, the central management entity 100 maypower on any management nodes, network switches, storage devices andserver nodes based on their ascending commonality among the devices inthe cluster. The relative commonality of each device may be used inconjunction with the power consumption per entity to pro-actively andintelligently limit the inrush current on each PDU.

In any server design, when the servers are connected to a powerdistribution circuit, the internal baseboard management controllersbecome active. Because of the low current draw, the amount of inrushcurrent across the entire installation is minimal and causes noproblems. Once the base board management controllers are operational,they are able to read the vital product data (VPD) of the server anddetermine the amount of power dissipated in the server planar. Themanagement entity which is connected to each BMC over an Ethernetnetwork can then communicate the power draw and current required foreach server. In addition, each PDU also has a service processor thatcommunicates with the central management entity.

Based upon data describing which servers receive power from which PDU,the management entity is then able to determine a total amount ofnominal current demand that is to be placed on each PDU. Similarly,based upon data describing which PDUs (and hence which servers) arelocated within a given rack, the management entity is able to determinea total amount of nominal current demand that is to be placed on eachrack. Furthermore, based upon data identifying the racks that arelocated in a cluster, the cluster management entity is able to determinea total amount of nominal current demand that is to be placed on thecluster. Once this current is calculated, the central management entityis able to systematically power on the entire cluster balancing theinrush current across the cluster and limiting the inrush current toeach individual PDU within a rack, and to each rack within the cluster.

In the situation where there are an equal number of two or moredifferent devices, as identified by tabulating the number of deviceshaving the same model identification codes, then the power up sequencemay use the device's network dependency criteria as a secondaryconsideration. For example, devices that provide fabrics like switches,management systems, and devices with VPD that indicate existence ofexternal storage may be powered on first. For example, if the centralmanagement entity determines that there are four x3650 M4 servers andfour network switches, the secondary consideration might weight in favorof powering on the four network switches prior to the four x2650 M4servers.

Basically, the management tool does a server power walk and associatesthe server power with each PDU. Once this information is tabulated, thenthe power draw per PDU can be calculated. Then the management toolselectively powers on the servers ensuring that the inrush current doesnot exceed the PDU specification. In addition, since the PDUs areconnected to AC power, the management tool can ensure that the inrushcurrent does not exceed the AC power ratings for the site.

Table 1, shown below, is a tabular representation of a power on sequenceto limit the inrush current.

TABLE 1 Power on sequencing Sequence PDU Server Power limit 1400 W PDU#1 42 450 2 41 350 1 40 350 2 39 550 1 38 450 2 37 450 1 36 450 3 • • •• • • • • • • • • 8 600 2 PDU #3 7 600 2 6 350 3 5 400 3 4 400 3 3 450 12 600 1 1 300 1

FIG. 6 is a diagram of an exemplary computing node (or simply“computer”) 102 that may be utilized in accordance with one or moreembodiments of the present invention. Note that some or all of theexemplary architecture, including both depicted hardware and software,shown for and within the computer 100 may be implemented in the centralmanagement entity shown in FIG. 5.

Computer 100 includes a processor unit 104 that is coupled to a systembus 106. Processor unit 104 may utilize one or more processors, each ofwhich has one or more processor cores. A video adapter 108, whichdrives/supports a display 110, is also coupled to system bus 106. In oneembodiment, a switch 107 couples the video adapter 108 to the system bus106. Alternatively, the switch 107 may couple the video adapter 108 tothe display 110. In either embodiment, the switch 107 is a switch,preferably mechanical, that allows the display 110 to be coupled to thesystem bus 106, and thus to be functional only upon execution ofinstructions that support the processes described herein.

System bus 106 is coupled via a bus bridge 112 to an input/output (I/O)bus 114. An I/O interface 116 is coupled to I/O bus 114. I/O interface116 affords communication with various I/O devices, including a keyboard118, a mouse 120, a media tray 122 (which may include storage devicessuch as CD-ROM drives, multi-media interfaces, etc.), a printer 124, and(if a VHDL chip 137 is not utilized in a manner described below),external USB port(s) 126. While the format of the ports connected to I/Ointerface 116 may be any known to those skilled in the art of computerarchitecture, in a preferred embodiment some or all of these ports areuniversal serial bus (USB) ports.

As depicted, the computer 100 is able to communicate over a network 128using a network interface 130. Network 128 may be an external networksuch as the Internet, or an internal network such as an Ethernet or avirtual private network (VPN).

A hard drive interface 132 is also coupled to system bus 106. Hard driveinterface 132 interfaces with a hard drive 134. In a preferredembodiment, hard drive 134 populates a system memory 136, which is alsocoupled to system bus 106. System memory is defined as a lowest level ofvolatile memory in computer 100. This volatile memory includesadditional higher levels of volatile memory (not shown), including, butnot limited to, cache memory, registers and buffers. Data that populatessystem memory 136 includes the computer's operating system (OS) 138 andapplication programs 144.

The operating system 138 includes a shell 140, for providing transparentuser access to resources such as application programs 144. Generally,shell 140 is a program that provides an interpreter and an interfacebetween the user and the operating system. More specifically, shell 140executes commands that are entered into a command line user interface orfrom a file. Thus, shell 140, also called a command processor, isgenerally the highest level of the operating system software hierarchyand serves as a command interpreter. The shell provides a system prompt,interprets commands entered by keyboard, mouse, or other user inputmedia, and sends the interpreted command(s) to the appropriate lowerlevels of the operating system (e.g., a kernel 142) for processing. Notethat while shell 140 is a text-based, line-oriented user interface, thepresent invention will equally well support other user interface modes,such as graphical, voice, gestural, etc.

As depicted, OS 138 also includes kernel 142, which includes lowerlevels of functionality for OS 138, including providing essentialservices required by other parts of OS 138 and application programs 144,including memory management, process and task management, diskmanagement, and mouse and keyboard management. Application programs 144in the system memory of computer 100 may include a cluster power onsequence control program 145. The system memory 136 may also store thePDU-Server Association Table 101, the PDU & Server Current Ratings Table102, and the Server Model Identification Code Table 103 for use in themethods described herein.

The system memory 136 may also include a VHDL (VHSIC hardwaredescription language) program. VHDL is an exemplary design-entrylanguage for field programmable gate arrays (FPGAs), applicationspecific integrated circuits (ASICs), and other similar electronicdevices. In one embodiment, execution of instructions from a VMPP causesa VHDL program to configure the VHDL chip 137, which may be an FPGA,ASIC, or the like.

In another embodiment of the present invention, execution ofinstructions from VMPP results in a utilization of VHDL program toprogram a VHDL emulation chip 151. VHDL emulation chip 151 mayincorporate a similar architecture as described above for VHDL chip 137.Once VMPP and VHDL program the VHDL emulation chip 151, VHDL emulationchip 151 performs, as hardware, some or all functions described by oneor more executions of some or all of the instructions found in VMPP.That is, the VHDL emulation chip 151 is a hardware emulation of some orall of the software instructions found in VMPP. In one embodiment, VHDLemulation chip 151 is a programmable read only memory (PROM) that, onceburned in accordance with instructions from VMPP and VHDL program, ispermanently transformed into a new circuitry that performs the functionsneeded to perform the processes of the present invention.

The hardware elements depicted in computer 100 are not intended to beexhaustive, but rather are representative devices suitable to performthe processes of the present invention. For instance, computer 100 mayinclude alternate memory storage devices such as magnetic cassettes,digital versatile disks (DVDs), Bernoulli cartridges, and the like.These and other variations are intended to be within the spirit andscope of the present invention.

FIG. 7 is a flowchart of a method 160 of the present invention in whicha management entity controls a power up sequence. In step 162, power isapplied to the central management entity. Then, in step 164, the centralmanagement entity walks the cluster configuration by communicating withthe BMC or service processor of each device in the cluster, includingthe servers, PDUs and network switches. The central management entitycollects various data, including the model identification codes for eachof the devices in the cluster, in order to determine the relativecommonality of the devices. The central management entity may thenassociate the servers and other network entities with a given one of thePDUs in step 166. The cluster power is tabulated in step 168, thecurrent limits for each PDU are set in step 170, and cluster entitiesare prioritized according to ascending commonality in step 172.

In step 174, power is turned on to the devices in a sequence ofascending commonality. Step 176 ensures that the cluster entities ordevices are drawing power that is under the PDU limit. Then in step 178,the method determines whether all of the cluster entities or devices arepowered on. If not, then the method returns to step 174. However, whenall of the devices are powered on, the method ends.

As will be appreciated by one skilled in the art, aspects of the presentinvention may be embodied as a system, method or computer programproduct. Accordingly, aspects of the present invention may take the formof an entirely hardware embodiment, an entirely software embodiment(including firmware, resident software, micro-code, etc.) or anembodiment combining software and hardware aspects that may allgenerally be referred to herein as a “circuit,” “module” or “system.”Furthermore, aspects of the present invention may take the form of acomputer program product embodied in one or more computer readablemedium(s) having computer readable program code embodied thereon.

Any combination of one or more computer readable medium(s) may beutilized. The computer readable medium may be a computer readable signalmedium or a computer readable storage medium. A computer readablestorage medium may be, for example, but not limited to, an electronic,magnetic, optical, electromagnetic, infrared, or semiconductor system,apparatus, or device, or any suitable combination of the foregoing. Morespecific examples (a non-exhaustive list) of the computer readablestorage medium would include the following: an electrical connectionhaving one or more wires, a portable computer diskette, a hard disk, arandom access memory (RAM), a read-only memory (ROM), an erasableprogrammable read-only memory (EPROM or Flash memory), an optical fiber,a portable compact disc read-only memory (CD-ROM), an optical storagedevice, a magnetic storage device, or any suitable combination of theforegoing. In the context of this document, a computer readable storagemedium may be any tangible medium that can contain, or store a programfor use by or in connection with an instruction execution system,apparatus, or device.

A computer readable signal medium may include a propagated data signalwith computer readable program code embodied therein, for example, inbaseband or as part of a carrier wave. Such a propagated signal may takeany of a variety of forms, including, but not limited to,electro-magnetic, optical, or any suitable combination thereof. Acomputer readable signal medium may be any computer readable medium thatis not a computer readable storage medium and that can communicate,propagate, or transport a program for use by or in connection with aninstruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmittedusing any appropriate medium, including but not limited to wireless,wireline, optical fiber cable, RF, etc., or any suitable combination ofthe foregoing.

Computer program code for carrying out operations for aspects of thepresent invention may be written in any combination of one or moreprogramming languages, including an object oriented programming languagesuch as Java, Smalltalk, C++ or the like and conventional proceduralprogramming languages, such as the “C” programming language or similarprogramming languages. The program code may execute entirely on theuser's computer, partly on the user's computer, as a stand-alonesoftware package, partly on the user's computer and partly on a remotecomputer or entirely on the remote computer or server. In the latterscenario, the remote computer may be connected to the user's computerthrough any type of network, including a local area network (LAN) or awide area network (WAN), or the connection may be made to an externalcomputer (for example, through the Internet using an Internet ServiceProvider).

Aspects of the present invention are described below with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems) and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer program instructions. These computer program instructions maybe provided to a processor of a general purpose computer, specialpurpose computer, or other programmable data processing apparatus toproduce a machine, such that the instructions, which execute via theprocessor of the computer or other programmable data processingapparatus, create means for implementing the functions/acts specified inthe flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computerreadable medium that can direct a computer, other programmable dataprocessing apparatus, or other devices to function in a particularmanner, such that the instructions stored in the computer readablemedium produce an article of manufacture including instructions whichimplement the function/act specified in the flowchart and/or blockdiagram block or blocks.

The computer program instructions may also be loaded onto a computer,other programmable data processing apparatus, or other devices to causea series of operational steps to be performed on the computer, otherprogrammable apparatus or other devices to produce a computerimplemented process such that the instructions which execute on thecomputer or other programmable apparatus provide processes forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof code, which comprises one or more executable instructions forimplementing the specified logical function(s). It should also be notedthat, in some alternative implementations, the functions noted in theblock may occur out of the order noted in the figures. For example, twoblocks shown in succession may, in fact, be executed substantiallyconcurrently, or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved. It will also be notedthat each block of the block diagrams and/or flowchart illustration, andcombinations of blocks in the block diagrams and/or flowchartillustration, can be implemented by special purpose hardware-basedsystems that perform the specified functions or acts, or combinations ofspecial purpose hardware and computer instructions.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the invention. Asused herein, the singular forms “a”, “an” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “comprises”and/or “comprising,” when used in this specification, specify thepresence of stated features, integers, steps, operations, elements,components and/or groups, but do not preclude the presence or additionof one or more other features, integers, steps, operations, elements,components, and/or groups thereof. The terms “preferably,” “preferred,”“prefer,” “optionally,” “may,” and similar terms are used to indicatethat an item, condition or step being referred to is an optional (notrequired) feature of the invention.

The corresponding structures, materials, acts, and equivalents of allmeans or steps plus function elements in the claims below are intendedto include any structure, material, or act for performing the functionin combination with other claimed elements as specifically claimed. Thedescription of the present invention has been presented for purposes ofillustration and description, but it is not intended to be exhaustive orlimited to the invention in the form disclosed. Many modifications andvariations will be apparent to those of ordinary skill in the artwithout departing from the scope and spirit of the invention. Theembodiment was chosen and described in order to best explain theprinciples of the invention and the practical application, and to enableothers of ordinary skill in the art to understand the invention forvarious embodiments with various modifications as are suited to theparticular use contemplated.

1-10. (canceled)
 11. A computer program product including computerusable program code embodied on a tangible computer usable storagemedium, the computer program product comprising: computer usable programcode for identifying a plurality of power distribution units disposed ina rack, wherein each power distribution units is connected to receivedpower from a main power source, and wherein each power distribution unitincludes a circuit breaker; computer usable program code for identifyinga plurality of devices disposed in the rack, wherein each device isconnected to receive power from one of the power distribution units, andwherein the plurality of devices are selected from server nodes, networkswitches and external data storage devices; computer usable program codefor obtaining vital product data from a service processor in eachdevice, wherein the vital product data identifies the device by a modelidentification code; and computer usable program code for powering on,for each of the power distribution units, the plurality of devices thatare connected to the power distribution unit in a sequence to prevent aninrush current from tripping the circuit breaker within the powerdistribution unit, wherein the sequence powers on devices in order ofascending commonality of the model identification code.
 12. The computerprogram product of claim 11, further comprising: computer usable programcode for determining the order of ascending commonality by tabulatingthe number of devices having a given model identification code andsorting a list of model identification codes from those having thefewest tabulated number of devices to those having the greatesttabulated number of devices.
 13. The computer program product of claim11, wherein the sequence includes powering on more than one of thedevices at a time.
 14. The computer program product of claim 11, furthercomprising: computer usable program code for waiting a predeterminedperiod of time between powering on any one or more device andsubsequently powering on any further device.
 15. The computer programproduct of claim 11, further comprising: computer usable program codefor identifying the rack position of each device with the rack, whereinthe rack position determines the power distribution unit to which thedevice is connected.
 16. The computer program product of claim 15,wherein the rack position of each device is identified by each devicedetecting a rack position and communicating the detected rack positionto a central management entity.
 17. The computer program product ofclaim 11, wherein the sequence of powering on the plurality of devicesalso prevents an inrush current from tripping a circuit breaker withinthe main power source that is connected to provide power to each of thepower distribution units.
 18. The computer program product of claim 11,further comprising: computer usable program code for determining a peakinrush current for each of the plurality of devices; computer usableprogram code for determining a current rating for the circuit breaker ineach of the plurality of power distribution units; and computer usableprogram code for determining that, for each of the plurality ofdistribution units, the sequence for powering on the plurality ofdevices will not cause a cumulative peak inrush current through thepower distribution unit to exceed the current rating for the circuitbreaker in the power distribution unit, wherein the cumulative peakinrush current is the sum of the peak inrush current through the powerdistribution unit to all of the devices being simultaneously powered onat any point in the sequence.
 19. The computer program product of claim18, wherein the peak inrush current for each device is a predeterminedmultiple of the nominal current rating of the device.
 20. The computerprogram product of claim 19, wherein the vital product data furtherincludes a nominal current rating of the device.